OK, the WSDL needs some additional content

Notes/Domino 8 Forum

Subject:

For consumer (script library WSDL import), the SAP WSDL needs to define an "output" message for the method, as well as an "input" message.

To do this, I added the following embellishments (boldfaced):

<wsdl:message name="empty"/>

<wsdl:portType name="mi_education_att_o">
<wsdl:operation name="mi_education_att_o">
<wsdl:input message="p1:mt_education_att_i" />
<wsdl:output message="p1:empty" />
</wsdl:operation>
</wsdl:portType>

<wsdl:binding name="mi_education_att_oBinding" type="p1:mi_education_att_o" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
<wsdl:operation name="mi_education_att_o">
<soap:operation soapAction="http://sap.com/xi/WebService/soap1.1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
<wsdl:input>
<soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>

The WSDL 1.1 spec talks about four "transmission primitives", of which we formally support only one, the so-called "Request-response" primitive. By adding the above "output" syntax, this instates that primitive in the WSDL, which will then successfully import into a consumer script library.

I'm not sure why provider Web service WSDL import is more forgiving in this respect -- we'll have to look further into that.

Feedback response number JGRN7AULZ3 created by ~Sven Xanrelyoopsi on 01/14/2008